Add support for JSON formatted Config files #14
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Looks good! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This pull request is intended to resolve #13.
Users will be able to pass in a JSON formatted configuration file as an option. This
configfile can contain any number of the options that this tool supports. Therefore, the user would not need to specify all options individually as command line argumentsFeatures
Code Changes
main.js line: 10to accept-c/--configarguments.readConfigFile) inmain.js line: 45to read and parse JSON files.readConfigFileif a config file is specified in the command line. Each option in the file will be passed intogenerateHTML